Skip to content

Draft blog post on FlowFuse Certified Nodes#5152

Open
KristopherLeads wants to merge 18 commits into
mainfrom
blog-why-certified
Open

Draft blog post on FlowFuse Certified Nodes#5152
KristopherLeads wants to merge 18 commits into
mainfrom
blog-why-certified

Conversation

@KristopherLeads

@KristopherLeads KristopherLeads commented Jun 5, 2026

Copy link
Copy Markdown
Contributor

Description

On request from ZJ: draft blog post for certified nodes.

Related Issue(s)

Checklist

  • I have read the contribution guidelines
  • I have considered the performance impact of these changes
  • Suitable unit/system level tests have been added and they pass
  • Documentation has been updated
  • For blog PRs, an Art Request has been created (instructions)

@netlify

netlify Bot commented Jun 5, 2026

Copy link
Copy Markdown

Deploy Preview for flowforge-website ready!

Name Link
🔨 Latest commit e0eee46
🔍 Latest deploy log https://app.netlify.com/projects/flowforge-website/deploys/6a47d72289d1f10008a67505
😎 Deploy Preview https://deploy-preview-5152--flowforge-website.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.
Lighthouse
Lighthouse
1 paths audited
Performance: 66 (🔴 down 1 from production)
Accessibility: 96 (no change from production)
Best Practices: 100 (no change from production)
SEO: 91 (no change from production)
PWA: -
View the detailed breakdown and full score reports

To edit notification comments on pull requests, go to your Netlify project configuration.

Comment thread src/blog/2026/06/why-flowfuse-certified-nodes.md Outdated
Comment thread src/blog/2026/06/why-flowfuse-certified-nodes.md Outdated
Comment thread src/blog/2026/06/why-flowfuse-certified-nodes.md Outdated

**Security:** FlowFuse proactively resolves potential vulnerabilities and revokes certification from any node that falls short - and notifies affected customers when that happens, so you're never the last to find out. Your nodes are secure by default - removing an entire headache from your workflow.

**Support:** When a Certified Node gives you trouble, you get real troubleshooting help and a defined path to resolution, not an unanswered issue queue. FlowFuse node certification also means FlowFuse supported - so you get real, human support, not automatically generated documentation that may or may not map to solutions.

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think the long term goal is to support each minor semver version for a decade. We cannot promise that today, but if you've built something now, it should continue to work and improve long term. (Performance etc)

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is that something we want to call out here, or do we want to be somewhat general in our public stance to give us flexibility?

Comment thread src/blog/2026/06/why-flowfuse-certified-nodes.md Outdated
Comment thread src/blog/2026/06/why-flowfuse-certified-nodes.md Outdated
Comment thread src/blog/2026/06/why-flowfuse-certified-nodes.md Outdated
Comment thread src/blog/2026/06/why-flowfuse-certified-nodes.md
KristopherLeads and others added 2 commits June 7, 2026 15:59
Co-authored-by: Zeger-Jan van de Weg <ZJvandeWeg@users.noreply.github.com>
Co-authored-by: Zeger-Jan van de Weg <ZJvandeWeg@users.noreply.github.com>
Adding liability comment based on #5152 (comment).
Updated text to emphasize the importance of security in handling sensitive data and the benefits of using Certified Nodes for compliance and risk management. #5152 (comment)
Added section about Certified Nodes and their benefits. #5152 (comment)
@KristopherLeads

KristopherLeads commented Jun 11, 2026

Copy link
Copy Markdown
Contributor Author

@ZJvandeWeg I added in a bunch of content to match these requests. Please take a look and let me know what you think. @PabloFilomeno83 let me know once you run your review.

Comment thread src/blog/2026/06/why-flowfuse-certified-nodes.md
Comment thread src/blog/2026/06/why-flowfuse-certified-nodes.md Outdated
Comment thread src/blog/2026/06/why-flowfuse-certified-nodes.md Outdated
Comment thread src/blog/2026/06/why-flowfuse-certified-nodes.md
Comment thread src/blog/2026/06/why-flowfuse-certified-nodes.md

FlowFuse certifies a node against three pillars, each aimed at a specific failure mode.

**Quality:** Every Certified Node is tested for operational reliability and compatibility, so it behaves predictably across versions instead of surprising you in production. This means no more guesswork, no more deep vetting, and significantly quicker time to value. We pick only the best-in-class OSS nodes, sub-license best-in-class properietary nodes, and build custom integrations for FlowFuse users. This means you get true best-in-class integrations in a single catalog - with no need to select new vendors or navigate complex licenses.

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is a bit too much AI for my taste. The bold combined with the :, it's offputting to me

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This was hand-generated so worrisome if it comes across that way. How does it read now - it has subheaders in h3.

title: "The what and the why: FlowFuse Certified Nodes"
subtitle: "Depend on maintained, secure, and supported nodes to reliably integrate your systems."
description: "FlowFuse Certified Nodes take the vetting, security monitoring, and support burden of community nodes off your plate. Read which four situations where they're the clear solve."
date: 2026-06-26

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Date needs to be updated


## Certified Ndoes Today

Right now, FlowFuse offers [Certified Nodes](https://flowfuse.com/integrations/?certified=1) across a wide variety of functions, offering official support for solutions like [ModBus](https://flowfuse.com/integrations/node-red-contrib-modbus/), [MongoDB](https://flowfuse.com/integrations/node-red-contrib-mongodb4/), [MCP](https://flowfuse.com/integrations/node-red-contrib-mcprotocol/), [OPC UA](https://flowfuse.com/node-red/flowfuse/edge/opcua/), and much more. We are constantly adding to this catalogue - with major additions planned in the coming weeks to expand this offering to even more devices and systems.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

These are the recommended nodes. Certified Nodes v2 includes a different set of nodes. You can check them here: https://flowfuse.com/integrations/


Right now, FlowFuse offers [Certified Nodes](https://flowfuse.com/integrations/?certified=1) across a wide variety of functions, offering official support for solutions like [ModBus](https://flowfuse.com/integrations/node-red-contrib-modbus/), [MongoDB](https://flowfuse.com/integrations/node-red-contrib-mongodb4/), [MCP](https://flowfuse.com/integrations/node-red-contrib-mcprotocol/), [OPC UA](https://flowfuse.com/node-red/flowfuse/edge/opcua/), and much more. We are constantly adding to this catalogue - with major additions planned in the coming weeks to expand this offering to even more devices and systems.

FlowFuse Certified Nodes are available to Teams and Enterprise tier customers. New instances get automatic access to the catalogue, and you can [contact us](https://flowfuse.com/contact-us) to add them to an existing instance - or to talk through which of these problems you're facing. Reach out to us today to see if FlowFuse Certified Nodes can help you and your stack!

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This needs to be updated to reflect the new offering

date: 2026-06-26
keywords: flowfuse certified nodes, node-red security, vetted nodes, node-red compliance, industrial node-red, node-red support, secure node-red deployment
authors: ["kristopher-sandoval"]
image:

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We need to add Blog tile ?

answer: "Much unplanned downtime comes from a node that ran fine for months breaking when an update shifts an underlying behavior. FlowFuse tests Certified Nodes for compatibility against the version they're meant to run on, which removes that class of surprise-upgrade failure — valuable for any operation measured in nines of availability."
- question: "What happens if a node loses certification?"
answer: "Certification revocation acts as an early-warning system. If a node you rely on stops meeting the security or quality bar, FlowFuse notifies affected customers, so you learn about the problem before it becomes an incident rather than discovering it in an outage."
- question: "Which FlowFuse tiers include Certified Nodes?"

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This needs to be updated to reflect the new offering

Comment thread src/blog/2026/06/why-flowfuse-certified-nodes.md Outdated
Comment thread src/blog/2026/06/why-flowfuse-certified-nodes.md Outdated
Comment thread src/blog/2026/06/why-flowfuse-certified-nodes.md Outdated
Comment thread src/blog/2026/06/why-flowfuse-certified-nodes.md Outdated
title: "The what and the why: FlowFuse Certified Nodes"
subtitle: "Depend on maintained, secure, and supported nodes to reliably integrate your systems."
description: "FlowFuse Certified Nodes take the vetting, security monitoring, and support burden of community nodes off your plate. Read which four situations where they're the clear solve."
date: 2026-06-26

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

you need to move blog to current month folder : 2026/07/

KristopherLeads and others added 5 commits July 3, 2026 08:33
Co-authored-by: sumit shinde ( Roni ) <110285294+sumitshinde-84@users.noreply.github.com>
Co-authored-by: sumit shinde ( Roni ) <110285294+sumitshinde-84@users.noreply.github.com>
Co-authored-by: sumit shinde ( Roni ) <110285294+sumitshinde-84@users.noreply.github.com>
Co-authored-by: sumit shinde ( Roni ) <110285294+sumitshinde-84@users.noreply.github.com>
FlowFuse certifies a node against three pillars, each aimed at a specific failure mode.

### Quality
Every Certified Node is tested for operational reliability and compatibility, so it behaves predictably across versions instead of surprising you in production. This means no more guesswork, no more deep vetting, and significantly quicker time to value. We pick only the best-in-class OSS nodes, sub-license best-in-class properietary nodes, and build custom integrations for FlowFuse users. This means you get true best-in-class integrations in a single catalog - with no need to select new vendors or navigate complex licenses.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
Every Certified Node is tested for operational reliability and compatibility, so it behaves predictably across versions instead of surprising you in production. This means no more guesswork, no more deep vetting, and significantly quicker time to value. We pick only the best-in-class OSS nodes, sub-license best-in-class properietary nodes, and build custom integrations for FlowFuse users. This means you get true best-in-class integrations in a single catalog - with no need to select new vendors or navigate complex licenses.
Every Certified Node is tested for reliability and compatibility, so it behaves consistently across versions and in production. This reduces the vetting work on your end and shortens time to value. We select proven open-source nodes, sub-license proprietary nodes where it makes sense, and build custom integrations when needed. The result is one catalogue of dependable integrations, without having to evaluate new vendors or manage separate licenses.

FlowFuse implements secure design and architecture by default, and this process extends to the Certified Nodes platform. Every node is checked, validated, and then secured via ongoing reviews per an SLA. This means that you don't stress, especially when fixes are time sensitive, converting a worry-mode update-fest to a smooth 5-minute task.

### Support
When a Certified Node gives you trouble, you get real troubleshooting help and a defined path to resolution, not an unanswered issue queue. FlowFuse node certification also means FlowFuse supported - so you get real, human support, not automatically generated documentation that may or may not map to solutions.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
When a Certified Node gives you trouble, you get real troubleshooting help and a defined path to resolution, not an unanswered issue queue. FlowFuse node certification also means FlowFuse supported - so you get real, human support, not automatically generated documentation that may or may not map to solutions.
When a Certified Node causes an issue, FlowFuse provides troubleshooting help and a clear path to resolution, rather than an open-ended issue queue. Certification also means FlowFuse support, so you're working with a person who can help, not just documentation that may or may not apply to your situation.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants